It is recommended that one builds the dependencies with VS10 as far as
possible, especially those from and using the GTK+ stack (i.e. GLib,
Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls
-to different CRTs can be kept at a minimum. zlib, libpng, and Cairo
-do contain support for compiling under VS10 using VS
-project files and/or makefiles at this time of writing, For the
+to different CRTs can be kept at a minimum.
+
+zlib, libpng, and Cairo do contain support for compiling under VS10
+using VS project files and/or makefiles at this time of writing, For the
GTK+ stack, VS10 project files are either available under
$(srcroot)/build/vs10 in the case of GLib (stable/unstable), ATK**
(2.x stable/unstable) and GDK-Pixbuf (unstable), and should be in the next
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)
+Unzip the binaries obtained from ftp.gnome.org in <root>\vs10\<PlatformName>,
+and build the following, if not already done so:
+
+Note: put the resulting zlib, libpng, pcre and Cairo files as follows:
+ .dll files: <root>\vs10\<PlatformName>\bin
+ .lib files: <root>\vs10\<PlatformName>\lib
+ .h files: <root>\vs10\<PlatformName>\include
+
The recommended build order for these dependencies:
(first unzip any dependent binaries downloaded from the ftp.gnome.org
as described in the README.txt file in the build/win32/vs10 folder)
-(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library]
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to
build PCRE is recommended-see build/win32/vs10/README.txt of GLib)
--GLib
+-GLib ***
-Cairo (inclusive of Cairo-GObject)
--ATK-2.x**
--Pango
--GDK-Pixbuf
+-ATK-2.x** ***
+-Pango***
+-GDK-Pixbuf***
(note the last 3 dependencies are not interdependent, so the last 3
dependencies can be built in any order)
project files higher in the stack are supposed to look for them, not
from a specific GLib source tree.
-*About the dependencies marked with *: I will see whether it is possible
- to reduce the depepdencies on building and running GTK+ by making these
- dependencies optional, as those are not compulsory components for
- building and running GTK+ itself, but note that they are needed for
- people running and building GIMP. They are referred to by components
- in Cairo and Pango mainly.
+*About the dependencies marked with *: These dependencies are optional
+ as those are not compulsory components for building and running GTK+
+ itself, but note that they are needed for people running and building
+ GIMP or those who need complex script support via fontconfig. They
+ are referred to by components in Cairo and Pango mainly.
+ Decide whether you need fontconfig support prior to building Cairo
+ and Pango.
**Regarding ATK-2.x: prior to compiling ATK-2.x, please open atkprops
in VS under "Properties Manager" view (it is under any one of the
this will be in the subsequent releases of ATK-2.x and was committed
upstream.
+***:Put the sources of the packages marked with *** in <root>\<package-
+ source-tree>, and build with VS10 from there.
+
--Tor Lillqvist <tml@iki.fi>
--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>
It is recommended that one builds the dependencies with VS9 as far as\r
possible, especially those from and using the GTK+ stack (i.e. GLib,\r
Cairo, ATK, Pango, GDK-Pixbuf), so that crashes caused by mixing calls\r
-to different CRTs can be kept at a minimum. zlib, libpng, and Cairo\r
-do contain support for compiling under VS9 using VS\r
-project files and/or makefiles at this time of writing, For the\r
+to different CRTs can be kept at a minimum. \r
+\r
+zlib, libpng, and Cairo do contain support for compiling under VS9\r
+using VS project files and/or makefiles at this time of writing, For the\r
GTK+ stack, VS9 project files are either available under\r
$(srcroot)/build/vs9 in the case of GLib (stable/unstable), ATK**\r
(2.x stable/unstable) and GDK-Pixbuf (unstable), and should be in the next\r
ftp://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32 bit)\r
ftp://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64 bit)\r
\r
+Unzip the binaries obtained from ftp.gnome.org in <root>\vs9\<PlatformName>,\r
+and build the following, if not already done so: \r
+\r
+Note: put the resulting zlib, libpng, pcre and Cairo files as follows:\r
+ .dll files: <root>\vs9\<PlatformName>\bin\r
+ .lib files: <root>\vs9\<PlatformName>\lib\r
+ .h files: <root>\vs9\<PlatformName>\include\r
+\r
The recommended build order for these dependencies:\r
(first unzip any dependent binaries downloaded from the ftp.gnome.org\r
as described in the README.txt file in the build/win32/vs9 folder)\r
-(for GDK-Pixbuf, if not using GDI+) jasper [jpeg-2000 library])\r
-(optional for GLib) PCRE (version 8.12 or later, use of CMake to\r
build PCRE is recommended-see build/win32/vs9/README.txt of GLib)\r
--GLib\r
+-GLib ***\r
-Cairo (inclusive of Cairo-GObject)\r
--ATK-2.x**\r
--Pango\r
--GDK-Pixbuf\r
+-ATK-2.x** ***\r
+-Pango***\r
+-GDK-Pixbuf***\r
(note the last 3 dependencies are not interdependent, so the last 3\r
dependencies can be built in any order)\r
\r
project files higher in the stack are supposed to look for them, not\r
from a specific GLib source tree.\r
\r
-*About the dependencies marked with *: I will see whether it is possible\r
- to reduce the depepdencies on building and running GTK+ by making these\r
- dependencies optional, as those are not compulsory components for\r
- building and running GTK+ itself, but note that they are needed for\r
- people running and building GIMP. They are referred to by components\r
- in Cairo and Pango mainly.\r
+*About the dependencies marked with *: These dependencies are optional\r
+ as those are not compulsory components for building and running GTK+\r
+ itself, but note that they are needed for people running and building\r
+ GIMP or those who need complex script support via fontconfig. They\r
+ are referred to by components in Cairo and Pango mainly.\r
+ Decide whether you need fontconfig support prior to building Cairo\r
+ and Pango.\r
\r
**Regarding ATK-2.x: prior to compiling ATK-2.x, please open atkprops\r
in VS under "Properties Manager" view (it is under any one of the\r
this will be in the subsequent releases of ATK-2.x and was committed\r
upstream.\r
\r
+***:Put the sources of the packages marked with *** in <root>\<package-\r
+ source-tree>, and build with VS9 from there.\r
+\r
--Tor Lillqvist <tml@iki.fi>\r
--Updated by Chun-wei Fan <fanc999@yahoo.com.tw>\r